home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Amiga Plus 1995 #5 & #6
/
Amiga Plus CD - 1995 - No. 5 and 6.iso
/
pd
/
netz
/
nntpd
/
man
/
relaynews.8
< prev
next >
Wrap
Text File
|
1995-08-16
|
9KB
|
265 lines
RELAYNEWS(8CN) RELAYNEWS(8CN)
NAME
relaynews - store and forward netnews articles
SYNOPSIS
uunews:bin/relay/relaynews [ -hsux ] [ -a dupsite ] [ -b
xrefsite ] [ -c currdir ] [ -d fhlmt ] [ -o days ]
DESCRIPTION
Relaynews installs locally and broadcasts (network) news
articles read from its standard input. Typically the
articles will be in a batch (see news(5)), which must not
be compressed (see compress(1)). Articles are usually
queued for transmission to one's netnews neighbours via
newsbatch(8CN) and thence via uux(1) or snntp(1).
-d turns on debugging of filing, headers, locking, match-
ing, transmission. -h prevents generation of history
entries for rejected articles; the default behaviour gen-
erates larger history files that allow NNTP receivers to
more efficiently reject offered articles. -s makes dis-
carding an article a serious matter, justifying a non-zero
exit status (for the benefit of inews). -c is an optimi-
sation: currdir is assumed to be the current directory; in
the absence of this option, pwd is invoked. -u unlinks
(removes) any filename arguments after successful process-
ing; they are assumed to be relative to currdir (`pwd` if
none). -o causes articles with dates (in Date: headers)
more than days old to be dropped (usually to stop acciden-
tally-retransmitted old articles).
-x prevents generation of Xref: headers in articles filed
in exactly one newsgroup; use of this option will inter-
fere with generation of news overview data and mirroring
via -b. -b causes relaynews to not update active and file
articles received directly from xrefsite under the groups
and article numbers found in incoming Xref: headers. -b
provides the basis for a news mirroring facility. -a sim-
ilarly causes active to not be updated and duplicate arti-
cles received directly from dupsite to be accepted, but
filed under the filenames found in their existing history
entries. It may be used to recover a news spool, given
recent active and history files.
Control messages, recognised by their Control: headers are
filed under the control pseudo-group only, but are for-
warded as usual, by examining their Newsgroups: and Dis-
tribution: headers. Note that posting to the control
pseudo-group will not cause a message to be treated as a
control message; control is not a real newsgroup.
An article which contains an Also-Control: header is
treated normally except that the contents of the header
are executed as if they were the contents of a Control:
header. Such an article is a form of hybrid message since
10 October 1993 1
RELAYNEWS(8CN) RELAYNEWS(8CN)
it functions as an ordinary article yet also causes con-
trol functions to be executed. The Supersedes: header is
a special case and is rewritten internally only to Also-
Control: cancel.
Articles which contain no locally-known (to the active
file) newsgroups yet accepted by the local subscription
list are filed exactly once, in the junk pseudo-group, and
forwarded as usual. If all newsgroups in the article are
refused by the local subscription list or are refused by
an x in active file entries, then the article will be dis-
carded and not filed in junk.
Locally-generated articles need not be permitted by the
local subscription list but are otherwise processed nor-
mally; this is for backward compatibility and perhaps to
keep the local subscription list short by not requiring
general and the like to be named.
EXAMPLES
cd uunews:/in.coming
relaynews -uc uunews:/in.coming -o 7 nntp.* >>uunews:/log 2>>uunews:/errlog"
File and forward articles in batches that arrived by
NNTP, and remove each batch upon successfully pro-
cessing it. Discard any articles more than a week
old.
FILES
uunews: netnews article tree
uunews:/comp/unix/wizards
example newsgroup directory (for
comp.unix.wizards); such directories
and their ancestor directories will be
created automatically as needed
uunews:/comp/unix/wizards/12564
example article file name
uunews:/out.going/system/togo
default sys file F, f, n and I flags
batch file name (N.B.:
uunews:/out.going/system will not be
automatically created as needed)
uunews:/sys determines who receives broadcast net-
news articles, which ones, and how
they are to be sent articles
uunews:/active contains locally-legal newsgroups and
(un)moderated flag
uunews:/history record of articles received and map-
ping of message-ids to file names
uunews:/history.{dir,pag}
dbm(3Z) index into history by message-
ids
uunews:/whoami if present, contains news system's
site name, overriding any other host
names
10 October 1993 2
RELAYNEWS(8CN) RELAYNEWS(8CN)
uunews:/log conventional log of incoming articles
uunews:/errlog conventional log of errors, should be
empty
uunews:/headers article headers of the last relaynews
invocation; consumed to generate
overview data
uunews:/bin system-specific directory of programs
to override uunews:bin and its subdi-
rectories
uunews:bin/ctl directory of programs to implement
control messages
uunews:bin/relay/relaynews
the lean, mean news-relayin' machine
uunews:bin/newsreply
generates a return address from arti-
cle headers uunews:/replyusepath tells
newsreply to use the Path header
rather than the From header for the
return address
SEE ALSO
compress(1), snntp(1), uux(1), dbm(3Z), news(5),
newsdb(5), newsbatch(8CN), rnews(8CN)
ARPA Internet RFCs 1036 and 850
DIAGNOSTICS
Usually found in uunews:/errlog.
Relaynews's exit status is 0 for successful completion, 1
if at least one batch was bad and worth manual inspection,
and 2 if the news system needs human attention.
If relaynews cannot establish safe standard file descrip-
tors and standardise its environment (notably PATH, SHELL
and IFS), probably due to failure of malloc(3), it will
exit with status of 1 and without writing any complaints
on standard error (errlog), as a (possibly-obsolete) secu-
rity precaution.
HISTORY
Written by Geoff Collyer at the University of Toronto as
part of the C news project.
BUGS
A control message which cannot be filed in the control
pseudo-group and which cannot be filed in the junk pseudo-
group because junk is not in the active file will generate
an error message which refers to the groups in its News-
groups: header instead of referring to the control pseudo-
group.
Relaynews could run faster in some circumstances and would
be simpler if Control: were required to be the first
header, if present, and if Newsgroups: were required to be
the next.
10 October 1993 3
RELAYNEWS(8CN) RELAYNEWS(8CN)
The whole control message and hybrid message situation is
a festering bug. Either control messages should be elimi-
nated, or all forms of backward compatibility should be
dropped (including Control: and Supersedes:) and only
Also-Control: should be supported.
10 October 1993 4